Triple
T35690716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anoat system |
E1031279
|
entity |
| Predicate | factionActivity |
P99629
|
FINISHED |
| Object | Imperial presence |
—
|
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: Imperial presence | Statement: [Anoat system, factionActivity, Imperial presence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionActivity Context triple: [Anoat system, factionActivity, Imperial presence]
-
A.
factionFocus
Indicates that an entity is primarily oriented toward, aligned with, or concentrated on a particular faction as its main focus.
-
B.
factionInvolved
chosen
Indicates that a particular faction participates in, is associated with, or plays a role in the specified event, situation, or context.
-
C.
factionContext
Indicates the broader group, side, or organizational alignment within which an entity’s actions, roles, or relationships take place.
-
D.
faction
Indicates that an entity is formally affiliated with, or belongs to, a particular faction or organized group within a broader context.
-
E.
factionUsage
Indicates how a particular faction is employed, involved, or utilized within a given context or situation.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:05 p.m.