Triple
T8492098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Traders |
E200995
|
entity |
| Predicate | hasFictionalGroup |
P75242
|
FINISHED |
| Object | Foundation traders |
—
|
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: Foundation traders | Statement: [The Traders, hasFictionalGroup, Foundation traders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalGroup Context triple: [The Traders, hasFictionalGroup, Foundation traders]
-
A.
partOfFictionalGroup
chosen
Indicates that an entity belongs to or is a member of a specific fictional group, organization, or team.
-
B.
usedByFictionalGroup
Indicates that something is utilized or employed by a fictional group or organization within a narrative context.
-
C.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
D.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
E.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
- F. None of above.
Provenance (3 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55cf5dc81908cad31ac53e15b46 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.