Triple
T5362638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National War Memorial |
E103056
|
entity |
| Predicate | hasInscribedNames |
P16756
|
FINISHED |
| Object | names of fallen Indian soldiers |
—
|
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 fallen Indian soldiers | Statement: [National War Memorial, hasInscribedNames, names of fallen Indian soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInscribedNames Context triple: [National War Memorial, hasInscribedNames, names of fallen Indian soldiers]
-
A.
hasInscriptions
chosen
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
B.
hasNumberOfNamesInscribed
Indicates the quantity of distinct names that are inscribed on a given entity.
-
C.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
-
D.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
E.
hasGivenNameUsage
Indicates that an entity is associated with a particular way or context in which its given name is used.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865b9b808190a1e8c283ba28d645 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.