Triple
T32052573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mickey’s Very Merry Christmas Party |
E818527
|
entity |
| Predicate | primaryLocationArea |
P203067
|
FINISHED |
| Object | Main Street, U.S.A. |
E185273
|
NE 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: Main Street, U.S.A. | Statement: [Mickey’s Very Merry Christmas Party, primaryLocationArea, Main Street, U.S.A.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLocationArea Context triple: [Mickey’s Very Merry Christmas Party, primaryLocationArea, Main Street, U.S.A.]
-
A.
primaryLocationIn
chosen
Indicates that an entity’s main or most significant location is within or at the referenced place.
-
B.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
C.
所在地エリア
Indicates the geographical area or region in which an entity is located or based.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
primarySurveyArea
Indicates that a specified area is the main or principal region targeted or covered by a particular survey or data collection activity.
- F. None of above.
Provenance (4 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46b9b138819097ee9f282fef86f2 |
completed | June 15, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:20 a.m.