Triple
T34531069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific/Norfolk |
E886536
|
entity |
| Predicate | languageNeutralIdentifier |
P3732
|
FINISHED |
| Object | Pacific/Norfolk |
—
|
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: Pacific/Norfolk | Statement: [Pacific/Norfolk, languageNeutralIdentifier, Pacific/Norfolk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageNeutralIdentifier Context triple: [Pacific/Norfolk, languageNeutralIdentifier, Pacific/Norfolk]
-
A.
languageNeutral
Indicates that the relationship or action is independent of any specific natural language, applying uniformly across different linguistic contexts.
-
B.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
standardIdentifier
Indicates that an entity is associated with a formally defined, standardized identifier used for consistent reference or cataloging.
-
D.
ianaIdentifierCase
Indicates that two IANA identifiers are related by a specific case-sensitivity or case-variation relationship.
-
E.
identitySymbol
Indicates that one entity serves as the symbolic representation or signifier of another entity’s identity.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a007241df8081909dbad651fda82aa7 |
completed | May 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_6a0071e77ed081908cd618da8977d878 |
completed | May 10, 2026, 11:54 a.m. |
Created at: May 1, 2026, 2:02 a.m.