Triple
T20001007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quint |
E494324
|
entity |
| Predicate | rankInBackstory |
P138300
|
FINISHED |
| Object | U.S. Navy sailor |
—
|
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: U.S. Navy sailor | Statement: [Quint, rankInBackstory, U.S. Navy sailor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInBackstory Context triple: [Quint, rankInBackstory, U.S. Navy sailor]
-
A.
protagonistRank
Indicates the relative narrative importance or centrality of a character within a story, typically ranking how primary they are as a protagonist compared to others.
-
B.
rankingRole
Indicates that one entity holds a specific position or level in an ordered hierarchy or ranking relative to others.
-
C.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
-
D.
rankAmongGods
Indicates how a being’s status or position compares relative to other gods within a divine hierarchy.
-
E.
rankWithinChapter
Indicates the relative ordering or position of an item among other items within the same chapter.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a222908190b88e1d11cb1b7ee3 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:32 p.m.