Triple
T48781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Pearl Harbor Remembrance Day |
E958
|
entity |
| Predicate | typicalActivities |
P1164
|
FINISHED |
| Object | memorial ceremonies |
—
|
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 ceremonies | Statement: [National Pearl Harbor Remembrance Day, typicalActivities, memorial ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalActivities Context triple: [National Pearl Harbor Remembrance Day, typicalActivities, memorial ceremonies]
-
A.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
C.
hasRecreationActivity
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
D.
mainCityCelebrations
Indicates that major celebratory events or festivities are held in or associated with a particular main city.
-
E.
introducedTo
Indicates that one entity caused or facilitated a first meeting or formal presentation between another entity and a third party.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.