Triple
T37456533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overmind |
E930813
|
entity |
| Predicate | strategicTrait |
P120775
|
FINISHED |
| Object | long-term planner |
—
|
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: long-term planner | Statement: [Overmind, strategicTrait, long-term planner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicTrait Context triple: [Overmind, strategicTrait, long-term planner]
-
A.
notableLeaderTrait
Indicates that the specified trait is a particularly prominent or defining characteristic of the leader in question.
-
B.
civilizationTrait
Indicates that a particular trait, characteristic, or cultural feature is associated with a given civilization.
-
C.
strategicAspect
chosen
Indicates that something pertains to a strategic dimension, such as long-term planning, positioning, or high-level decision-making within a broader context.
-
D.
loreTrait
Indicates that an entity possesses a specific lore-related characteristic or attribute within a fictional or narrative context.
-
E.
factionCharacteristic
Indicates that a particular characteristic, trait, or property is associated with or defines a given faction.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.