Triple
T15482592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock, Texas |
E376955
|
entity |
| Predicate | hasLevelOfIncorporation |
P69304
|
FINISHED |
| Object | unincorporated |
—
|
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: unincorporated | Statement: [Brock, Texas, hasLevelOfIncorporation, unincorporated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelOfIncorporation Context triple: [Brock, Texas, hasLevelOfIncorporation, unincorporated]
-
A.
incorporatedStatus
chosen
Indicates whether an entity has been legally formed and registered as a corporation or similar incorporated organization.
-
B.
incorporationType
Indicates the legal form or category under which an entity is formally incorporated or registered as an organization.
-
C.
hasLegalStructure
Indicates that an entity possesses a specific formal legal organization or classification under law.
-
D.
statusBeforeIncorporation
Indicates the legal or organizational status an entity held prior to its formal incorporation.
-
E.
underlyingIncorporatedIn
Indicates that one entity serves as the foundational or base component that has been formally included or integrated into another 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8cb4388190a3b4c92c3bb4ad4f |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:40 a.m.