Triple
T31453842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliza McCartney |
E802393
|
entity |
| Predicate | recordScope |
P182759
|
FINISHED |
| Object | national record of New Zealand |
—
|
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: national record of New Zealand | Statement: [Eliza McCartney, recordScope, national record of New Zealand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordScope Context triple: [Eliza McCartney, recordScope, national record of New Zealand]
-
A.
recordingScope
chosen
Indicates the extent, boundaries, or range of content, time, or context that a particular recording covers or applies to.
-
B.
reservationScope
Indicates the extent or range within which a reservation applies or is valid.
-
C.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
D.
recordLayer
Indicates that one entity documents or stores information about another entity within a specific layer or level of a system or structure.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 30, 2026, 9:15 p.m.