Triple
T30579999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reflecting Absence |
E778356
|
entity |
| Predicate | hasNameInscribed |
P195685
|
FINISHED |
| Object | names of victims of the September 11, 2001 attacks |
—
|
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: names of victims of the September 11, 2001 attacks | Statement: [Reflecting Absence, hasNameInscribed, names of victims of the September 11, 2001 attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInscribed Context triple: [Reflecting Absence, hasNameInscribed, names of victims of the September 11, 2001 attacks]
-
A.
hasNumberOfNamesInscribed
Indicates the quantity of distinct names that are inscribed on a given entity.
-
B.
hasNoNamesInscribed
Indicates that the entity lacks any names written, carved, or otherwise inscribed on it.
-
C.
mayBeInscribedOn
Indicates that one entity is permitted or suitable to be written, engraved, or otherwise inscribed on another entity.
-
D.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
E.
hasTitleInInscription
Indicates that an entity is mentioned with a specific title or designation within an inscription.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69fddf70ab10819088b76bd98e208354 |
completed | May 8, 2026, 1:04 p.m. |
Created at: April 29, 2026, 8:23 p.m.