Triple
T11336715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | secretariat of state |
E268488
|
entity |
| Predicate | canBeFoundIn |
P9687
|
FINISHED |
| Object | unitary states |
—
|
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: unitary states | Statement: [secretariat of state, canBeFoundIn, unitary states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeFoundIn Context triple: [secretariat of state, canBeFoundIn, unitary states]
-
A.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
C.
foundInSpecies
Indicates that something (such as a feature, gene, or characteristic) occurs in, is present in, or is observed within a particular species.
-
D.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
E.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.