Triple
T28036062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcelain Capital |
E708410
|
entity |
| Predicate | hasReputationScope |
P199168
|
FINISHED |
| Object | international |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: international | Statement: [Porcelain Capital, hasReputationScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReputationScope Context triple: [Porcelain Capital, hasReputationScope, international]
-
A.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
B.
providesReputationWith
Indicates that one entity grants or assigns a reputation value, score, or status to another entity.
-
C.
hasInUniverseReputation
Indicates that an entity holds a particular level or type of reputation within a specified fictional or conceptual universe.
-
D.
hasAffiliationScope
Indicates the scope or extent within which an affiliation or association between entities is valid or applies.
-
E.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
| PDg | Predicate description generation | batch_69ff246d53cc81909d5528224149b04b |
completed | May 9, 2026, 12:11 p.m. |
Created at: April 27, 2026, 8:21 p.m.