Triple
T35470107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbital Drop Shock Troopers |
E1025184
|
entity |
| Predicate | distinctionFromSpartans |
P183321
|
FINISHED |
| Object | non-augmented human soldiers |
—
|
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: non-augmented human soldiers | Statement: [Orbital Drop Shock Troopers, distinctionFromSpartans, non-augmented human soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinctionFromSpartans Context triple: [Orbital Drop Shock Troopers, distinctionFromSpartans, non-augmented human soldiers]
-
A.
objectiveOfSparta
Indicates that a particular goal, aim, or purpose is associated with Sparta.
-
B.
roleInTrojanWar
Indicates the specific function, position, or part an entity played in the events of the Trojan War.
-
C.
distanceFromSparta
Indicates the spatial distance separating a given entity or location from Sparta.
-
D.
roleInBattleOfSalamis
Indicates the specific role or involvement an entity had in the Battle of Salamis.
-
E.
AthenianCommander
Indicates that the subject serves as a military commander for the Athenians or the Athenian state.
- 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_69f76dfa20d0819089585dc2cf653aea |
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.