Triple
T30030425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLW |
E762998
|
entity |
| Predicate | isGeographicCode |
P168367
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [TLW, isGeographicCode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeographicCode Context triple: [TLW, isGeographicCode, true]
-
A.
hasGeographicType
Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
-
B.
hasGeocode
Indicates that an entity is associated with a specific geographic coordinate or coded location reference.
-
C.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
D.
isGeographicTitle
Indicates that a title or designation specifically refers to a geographic location or region.
-
E.
geographicCriterion
Indicates that the relationship or selection is determined based on geographic factors, such as location, region, or spatial boundaries.
- F. None of above. chosen
Provenance (4 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679af17648190bc90c5dc4afe35e4 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:49 p.m.