Triple
T35727194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IN-PB |
E1032645
|
entity |
| Predicate | abbreviationOfSubdivisionName |
P11177
|
FINISHED |
| Object | PB |
—
|
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: PB | Statement: [IN-PB, abbreviationOfSubdivisionName, PB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationOfSubdivisionName Context triple: [IN-PB, abbreviationOfSubdivisionName, PB]
-
A.
divisionAbbreviation
chosen
Indicates that one entity is the standard shortened or abbreviated form of the name of a division associated with another entity.
-
B.
subdivisionOfName
Indicates that the given name is the name of a larger administrative or territorial unit of which the subject entity is a subdivision.
-
C.
provincialSubdivisionName
Indicates the name assigned to a first-level administrative or provincial subdivision within a larger territorial or political entity.
-
D.
subdivisionNameType
Indicates the type or category of a named geographic or administrative subdivision (e.g., province, state, district) associated with an entity.
-
E.
scriptOfSubdivisionNames
Indicates that the specified writing system or script is used to represent the names of the subdivisions of a given entity.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.