Triple
T4492216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B12 |
E100602
|
entity |
| Predicate | isAutonomyConference |
P56880
|
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: [B12, isAutonomyConference, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAutonomyConference Context triple: [B12, isAutonomyConference, true]
-
A.
isNonGeographicConference
Indicates that a conference is defined by non-geographic criteria (such as topic, organization, or virtual nature) rather than by a specific physical location.
-
B.
isMultiStateConference
Indicates that a conference involves participants or activities spanning multiple states rather than being limited to a single state.
-
C.
parallelConference
Indicates that two or more conferences occur at the same time or overlap in schedule, running in parallel to each other.
-
D.
proceedingsAre
Indicates that certain events, actions, or legal steps constitute or are recognized as formal proceedings.
-
E.
governingConference
Indicates that one entity serves as the official organizing or regulatory conference overseeing another entity (such as a team, event, or institution).
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd556f99b48190ae60506a35b43c29 |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 12:59 p.m.