Triple
T4752969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Rico |
E105519
|
entity |
| Predicate | preServiceStatus |
P58556
|
FINISHED |
| Object | civilian of the Terran Federation |
—
|
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: civilian of the Terran Federation | Statement: [Johnny Rico, preServiceStatus, civilian of the Terran Federation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preServiceStatus Context triple: [Johnny Rico, preServiceStatus, civilian of the Terran Federation]
-
A.
preStandardizationStatus
Indicates the status or condition of something before it undergoes a standardization process.
-
B.
preStateFunction
Indicates that a function or system is in a specific state or configuration before a particular action, event, or transition occurs.
-
C.
typicalServiceStatus
Indicates the usual or standard operational state or condition that a service is expected to be in under normal circumstances.
-
D.
hasPreCodeStatus
Indicates that an entity held a specific code-related status or classification at some earlier point in time.
-
E.
programStatus
Indicates the current state or condition of a program within its lifecycle (e.g., planned, active, paused, completed, or terminated).
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e5fba88190b1f28d1b0eed3f8e |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6424a1d08190ac1d5fc574dc1b55 |
completed | March 20, 2026, 3:13 p.m. |
Created at: March 20, 2026, 1:20 p.m.