Triple
T35471483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tower |
E1025218
|
entity |
| Predicate | hasVendor |
P183326
|
FINISHED |
| Object | Cryptarch |
—
|
NE NERFINISHED |
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: Cryptarch | Statement: [The Tower, hasVendor, Cryptarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVendor Context triple: [The Tower, hasVendor, Cryptarch]
-
A.
supportsVendor
Indicates that one entity provides assistance, resources, or endorsement to a vendor in carrying out its activities or services.
-
B.
supportsHardwareVendor
Indicates that one entity provides assistance, resources, or endorsement to a hardware vendor in fulfilling its products or services.
-
C.
hasTypeOfVendor
Indicates that an entity is associated with or classified under a specific category or type of vendor.
-
D.
usesHardwareVendor
Indicates that one entity relies on or employs the hardware products or services provided by a specific hardware vendor.
-
E.
hasReactorVendor
Indicates that one entity serves as the supplier or manufacturer of a reactor for another entity.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.