Triple
T4641247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian War Cemetery at El Alamein |
E101659
|
entity |
| Predicate | hasCrossesOrMarkers |
P30330
|
FINISHED |
| Object | individual grave markers |
—
|
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: individual grave markers | Statement: [Italian War Cemetery at El Alamein, hasCrossesOrMarkers, individual grave markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossesOrMarkers Context triple: [Italian War Cemetery at El Alamein, hasCrossesOrMarkers, individual grave markers]
-
A.
hasNumberOfCrosses
Indicates the quantity of crosses associated with or present on a given entity.
-
B.
hasCross
chosen
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
C.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
-
D.
hasCrossColor
Indicates that an entity possesses a cross-shaped marking or pattern of a specified color.
-
E.
hasMarker
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a91b7748190b0b080af76e7b39f |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.