Triple
T23404143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wheeling metropolitan area |
E559587
|
entity |
| Predicate | isMultiState |
P152129
|
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: [Wheeling metropolitan area, isMultiState, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultiState Context triple: [Wheeling metropolitan area, isMultiState, true]
-
A.
isMultiStateConference
Indicates that a conference involves participants or activities spanning multiple states rather than being limited to a single state.
-
B.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
C.
isMultiSectional
Indicates that something is composed of or divided into multiple distinct sections or parts.
-
D.
isMultiPurpose
Indicates that something is designed or used to serve multiple functions or purposes rather than a single, specialized one.
-
E.
hasMultipleUnitControl
Indicates that a single controller or agent is able to direct, manage, or operate more than one unit simultaneously.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e27db88190b37375b38073291c |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:37 p.m.