Triple
T38174555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon a 2 |
E1000168
|
entity |
| Predicate | hasSurvivingScore |
P11769
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Canon a 2, hasSurvivingScore, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurvivingScore Context triple: [Canon a 2, hasSurvivingScore, true]
-
A.
hasSurvivalStatus
Indicates the survival condition or outcome associated with an entity, such as whether it is alive, deceased, or in another defined survival state.
-
B.
hasSurvivorTerm
Indicates that an entity is associated with a term or label specifically used to describe survivors of an event, condition, or circumstance.
-
C.
hasSurvivalElements
Indicates that something includes features or conditions related to survival, such as resource management, threat avoidance, or sustaining life over time.
-
D.
hasSurvivors
chosen
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
-
E.
hasScoreBy
Indicates that one entity possesses or is associated with a score that was assigned, produced, or determined by another entity.
- F. None of above.
Provenance (3 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4:29 p.m.