Triple
T32093533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richie Mo'unga |
E819663
|
entity |
| Predicate | cityOfPrimaryActivity |
P136244
|
FINISHED |
| Object | Christchurch |
—
|
NE NERFINISHED |
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: Christchurch | Statement: [Richie Mo'unga, cityOfPrimaryActivity, Christchurch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfPrimaryActivity Context triple: [Richie Mo'unga, cityOfPrimaryActivity, Christchurch]
-
A.
primaryUseCity
Indicates that a city is the main or principal location where something (such as a service, facility, or entity) is primarily used or operates.
-
B.
majorEmployerCity
Indicates that a city is a primary or significant employer of a given entity (such as an organization or population).
-
C.
cityOfMajorPresence
Indicates that an entity has a significant or primary operational, demographic, or functional presence in the specified city.
-
D.
primaryLocationCity
chosen
Indicates the city that serves as the main or primary location associated with the subject.
-
E.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:25 a.m.