Triple
T15443689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatican City passport |
E369972
|
entity |
| Predicate | holderMayAlsoHold |
P24187
|
FINISHED |
| Object | another national passport (in some cases) |
—
|
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: another national passport (in some cases) | Statement: [Vatican City passport, holderMayAlsoHold, another national passport (in some cases)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderMayAlsoHold Context triple: [Vatican City passport, holderMayAlsoHold, another national passport (in some cases)]
-
A.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of another entity.
-
B.
alsoHolds
chosen
Indicates that a condition, property, or relation that applies in one context or case simultaneously applies in another context or case.
-
C.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
D.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
E.
holdsTo
Indicates that one entity maintains, adheres, or remains committed to another entity, such as a belief, standard, agreement, or condition.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef666e08190a02a01a676306ab9 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.