Triple
T496549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand dollar |
E10305
|
entity |
| Predicate | reasonForNickName |
P7596
|
FINISHED |
| Object | association with New Zealand national bird kiwi |
—
|
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: association with New Zealand national bird kiwi | Statement: [New Zealand dollar, reasonForNickName, association with New Zealand national bird kiwi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNickName Context triple: [New Zealand dollar, reasonForNickName, association with New Zealand national bird kiwi]
-
A.
reasonForNickname
chosen
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
B.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
D.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
-
E.
localNickname
Indicates that an entity is known by a particular nickname within a specific local or regional 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f116f1b4819082f88d6c747368ae |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.