Triple
T30579938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ground Zero |
E778355
|
entity |
| Predicate | primaryUseAfter2001 |
P69258
|
FINISHED |
| Object | memorial |
—
|
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: memorial | Statement: [Ground Zero, primaryUseAfter2001, memorial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseAfter2001 Context triple: [Ground Zero, primaryUseAfter2001, memorial]
-
A.
primaryUseInEarly2000s
Indicates that something was mainly or most commonly used during the early 2000s time period.
-
B.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
C.
primaryUseStart
Indicates the point in time or event at which the primary use or main function of something begins.
-
D.
laterPrimarilyUsedFor
chosen
Indicates that something was initially used for one purpose but, at a later time, came to be used mainly for another specified purpose.
-
E.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0302d9d2d88190b20429530775b035 |
completed | May 12, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_6a0302289128819085428f3d544c2fb9 |
completed | May 12, 2026, 10:34 a.m. |
Created at: April 29, 2026, 8:23 p.m.