Triple
T250887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas legislative districts |
E5143
|
entity |
| Predicate | hasMap |
P103
|
FINISHED |
| Object | Texas legislative district map |
—
|
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: Texas legislative district map | Statement: [Texas legislative districts, hasMap, Texas legislative district map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMap Context triple: [Texas legislative districts, hasMap, Texas legislative district map]
-
A.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
B.
hasRepresentationIn
chosen
Indicates that one entity is represented, depicted, or encoded within another entity, such as a concept, object, or data structure having a corresponding representation in a specific medium or context.
-
C.
hasObject
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
-
D.
hasMarker
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
E.
hasTree
Indicates that one entity possesses, contains, or is associated with a tree.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.