Triple
T30007550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LBA |
E762364
|
entity |
| Predicate | unitOfAddressing |
P98440
|
FINISHED |
| Object | block |
—
|
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: block | Statement: [LBA, unitOfAddressing, block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitOfAddressing Context triple: [LBA, unitOfAddressing, block]
-
A.
designationUnit
chosen
Indicates that one entity serves as the unit or standard of measure used to designate, label, or quantify another entity.
-
B.
hasUnitNumber
Indicates that an entity is associated with a specific unit identifier or number within a larger building, complex, or organizational structure.
-
C.
baseUnitNumber
Indicates the identifying number assigned to a primary or foundational unit within a larger system or structure.
-
D.
basicUnitOf
Indicates that one entity serves as the fundamental or smallest constituent unit from which the other entity is composed or defined.
-
E.
typeOfUnitStructure
Indicates that one unit is classified as having a particular structural type or organizational form.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67953393481909fce15619f1a1c10 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:43 p.m.