Triple
T35842136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woden, Texas |
E1036111
|
entity |
| Predicate | hasZIPCodeSharedWith |
P136734
|
FINISHED |
| Object | Nacogdoches, Texas |
—
|
NE NERFINISHED |
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: Nacogdoches, Texas | Statement: [Woden, Texas, hasZIPCodeSharedWith, Nacogdoches, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZIPCodeSharedWith Context triple: [Woden, Texas, hasZIPCodeSharedWith, Nacogdoches, Texas]
-
A.
sharesZIPCodeWith
chosen
Indicates that two entities are located in areas that have the same ZIP or postal code.
-
B.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
C.
postalServiceSharedWith
Indicates that two or more entities use or are served by the same postal service or postal delivery system.
-
D.
isSharedByFamily
Indicates that something is commonly used, owned, or enjoyed by multiple members of the same family.
-
E.
sharesProvinceWith
Indicates that two entities are located within, or associated with, the same administrative province.
- 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_69f76e1a29e8819088280f26096aeb55 |
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:06 p.m.