Triple
T31672645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook Islands passport |
E808312
|
entity |
| Predicate | identifiesBy |
P3732
|
FINISHED |
| Object | passport number |
—
|
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: passport number | Statement: [Cook Islands passport, identifiesBy, passport number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesBy Context triple: [Cook Islands passport, identifiesBy, passport number]
-
A.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
B.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
helpsIdentify
Indicates a relationship where one entity serves to distinguish, recognize, or determine the identity or characteristics of another entity.
-
D.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
E.
identifiesMembersBy
Indicates that one entity specifies or determines the individual members that belong to another entity or group.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 30, 2026, 11:01 p.m.