Triple
T20856799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secular Order of Discalced Carmelites |
E513500
|
entity |
| Predicate | hasLocalUnits |
P129318
|
FINISHED |
| Object | local communities |
—
|
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: local communities | Statement: [Secular Order of Discalced Carmelites, hasLocalUnits, local communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalUnits Context triple: [Secular Order of Discalced Carmelites, hasLocalUnits, local communities]
-
A.
isLocalQuantity
Indicates that a quantity is specific to a particular context, location, or subsystem rather than being globally applicable.
-
B.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
C.
hasBasedUnits
Indicates that a derived measurement unit is defined in terms of one or more underlying base units.
-
D.
hasUnitStructure
Indicates that an entity possesses a specific internal organization or arrangement that defines its structural composition.
-
E.
hasLocalities
chosen
Indicates that an entity is associated with, contains, or is linked to one or more specific geographic or administrative local areas.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a93ea881909b9f80a9bd0605b6 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.