Triple
T30228726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Navy |
E768565
|
entity |
| Predicate | statusAfterCloneWars |
P194705
|
FINISHED |
| Object | absorbed into Imperial Navy |
—
|
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: absorbed into Imperial Navy | Statement: [Republic Navy, statusAfterCloneWars, absorbed into Imperial Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterCloneWars Context triple: [Republic Navy, statusAfterCloneWars, absorbed into Imperial Navy]
-
A.
politicalStatusDuringCloneWars
Indicates the political alignment or affiliation an entity held during the period of the Clone Wars.
-
B.
statusAfterBattleOfYavin
Indicates the condition or state of an entity following the Battle of Yavin.
-
C.
roleDuringCloneWars
Indicates the specific function, position, or duties an entity held during the time period of the Clone Wars.
-
D.
statusInRogueOne
Indicates the role or condition an entity has specifically within the context of the film "Rogue One," such as whether and how it appears or participates in that storyline.
-
E.
roleDuringGalacticCivilWar
Indicates the specific function, position, or involvement an entity had during the Galactic Civil War.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
| PDg | Predicate description generation | batch_69fd82ebe1c081908455fc45b6e45178 |
completed | May 8, 2026, 6:30 a.m. |
Created at: April 29, 2026, 7:36 p.m.