Triple
T4370951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lone Pine Cemetery |
E98893
|
entity |
| Predicate | numberOfCommemoratedOnMemorial |
P4086
|
FINISHED |
| Object | over 4,900 |
—
|
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: over 4,900 | Statement: [Lone Pine Cemetery, numberOfCommemoratedOnMemorial, over 4,900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfCommemoratedOnMemorial Context triple: [Lone Pine Cemetery, numberOfCommemoratedOnMemorial, over 4,900]
-
A.
numberOfCommemoratedPersons
chosen
Indicates the count of distinct persons who are commemorated or honored in a given context or entity.
-
B.
commemoratedOn
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
C.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
D.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
E.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521cb7ec8190b7b79675871d97d8 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.