Triple
T3377742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Corsair |
E71106
|
entity |
| Predicate | timeLordSocietyStatus |
P48094
|
FINISHED |
| Object | renegade |
—
|
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: renegade | Statement: [the Corsair, timeLordSocietyStatus, renegade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeLordSocietyStatus Context triple: [the Corsair, timeLordSocietyStatus, renegade]
-
A.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
B.
timeStatus
Indicates the temporal state or condition of an event or entity relative to a reference time (e.g., past, present, future, ongoing, or scheduled).
-
C.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
D.
titleHolderSince
Indicates the entity that has held a particular title or position continuously from a specified starting time.
-
E.
timePeriodOfDominance
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e8d1988190b6fb6c4c5502f25f |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69adaa518ac88190b64f949ace018ab7 |
completed | March 8, 2026, 4:56 p.m. |
Created at: March 8, 2026, 3:13 p.m.