Triple
T5746160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee–North Carolina border |
E126736
|
entity |
| Predicate | formsTimeZoneBoundary |
P53378
|
FINISHED |
| Object | partly |
—
|
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: partly | Statement: [Tennessee–North Carolina border, formsTimeZoneBoundary, partly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsTimeZoneBoundary Context triple: [Tennessee–North Carolina border, formsTimeZoneBoundary, partly]
-
A.
timeZoneBoundaryFor
chosen
Indicates that a given boundary or geographic region serves as the delimiting line for a specific time zone.
-
B.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
C.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
D.
offsetRangeOfTimeZones
Indicates that one entity specifies the span or limits of time zone offsets (e.g., from minimum to maximum UTC offsets) applicable to another entity.
-
E.
relatedTimeZone
Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.