Triple
T29953562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BR 60800 Green Arrow |
E760833
|
entity |
| Predicate | survivingExamplesOfClass |
P148895
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [BR 60800 Green Arrow, survivingExamplesOfClass, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingExamplesOfClass Context triple: [BR 60800 Green Arrow, survivingExamplesOfClass, 1]
-
A.
survivingExample
chosen
Indicates that one entity is a remaining, extant, or still-existing instance or specimen of another entity.
-
B.
survivorOfClass
Indicates that one entity is a surviving member or remnant of a particular class, group, or category that has otherwise been diminished or eliminated.
-
C.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
D.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
-
E.
survivedBy
Indicates that one entity continues to live or exist after the death or end of 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6783880608190906379178b865dc0 |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:26 p.m.