Triple
T35471387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exo |
E1025216
|
entity |
| Predicate | hasPurposeInLore |
P97516
|
FINISHED |
| Object | military combat |
—
|
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: military combat | Statement: [Exo, hasPurposeInLore, military combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPurposeInLore Context triple: [Exo, hasPurposeInLore, military combat]
-
A.
designedPurposeInFiction
Indicates that something is intentionally created within a fictional context to serve a particular role, function, or narrative purpose.
-
B.
primaryFunctionInLore
chosen
Indicates that something’s main role or purpose is defined within a fictional or narrative lore context.
-
C.
hasDramaticPurpose
Indicates that something serves a specific dramatic function or role within a narrative or performance.
-
D.
findsPurposeThrough
Indicates that one entity derives its sense of purpose, meaning, or fulfillment through its relationship with or actions involving another entity.
-
E.
hasFictionalBackstory
Indicates that an entity is associated with an invented or imaginary narrative background rather than a real-world history.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:04 p.m.