Triple
T29878171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TIE Defender |
E758798
|
entity |
| Predicate | factionUsage |
P167698
|
FINISHED |
| Object | Imperial Navy |
—
|
NE NERFINISHED |
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 Navy | Statement: [TIE Defender, factionUsage, Imperial Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionUsage Context triple: [TIE Defender, factionUsage, Imperial Navy]
-
A.
factionRole
Indicates the specific role, function, or position an entity holds within a particular faction or group.
-
B.
factionFocus
Indicates that an entity is primarily oriented toward, aligned with, or concentrated on a particular faction as its main focus.
-
C.
factionType
Indicates the classification or category of a faction within a broader system or context.
-
D.
factionContext
Indicates the broader group, side, or organizational alignment within which an entity’s actions, roles, or relationships take place.
-
E.
factionInvolved
Indicates that a particular faction participates in, is associated with, or plays a role in the specified event, situation, or context.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676caee048190952d49763046a768 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:56 p.m.