Triple
T33691446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent Thameside |
E863191
|
entity |
| Predicate | hasMajorFocus |
P203139
|
FINISHED |
| Object | large-scale housing development |
—
|
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: large-scale housing development | Statement: [Kent Thameside, hasMajorFocus, large-scale housing development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorFocus Context triple: [Kent Thameside, hasMajorFocus, large-scale housing development]
-
A.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
B.
hasMajorCategory
Indicates that something is associated with or classified under a primary, overarching category.
-
C.
hasImpactFocus
Indicates that an entity is primarily concerned with or directed toward a particular type or area of impact.
-
D.
hasSingleMajor
Indicates that an entity (such as a student or academic program) is associated with exactly one major field of study.
-
E.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0127c36dc08190b07765756b3d0e1b |
completed | May 11, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_6a0125ef57208190be5b5e761fcae981 |
completed | May 11, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_6a0127c27a888190a530763f4216e7d5 |
completed | May 11, 2026, 12:50 a.m. |
Created at: May 1, 2026, 1:43 a.m.