Triple
T25902472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowling |
E652654
|
entity |
| Predicate | featuresSplitPerspective |
P180921
|
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: [Bowling, featuresSplitPerspective, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSplitPerspective Context triple: [Bowling, featuresSplitPerspective, true]
-
A.
featuresPerspective
Indicates that one entity presents, embodies, or incorporates the viewpoint, angle, or outlook provided by another entity.
-
B.
featuresSegment
Indicates that one entity includes or highlights a particular segment or portion of another entity as a notable part of it.
-
C.
exploresPerspectiveOf
Indicates that one entity examines, investigates, or considers the viewpoint, stance, or outlook associated with another entity.
-
D.
featuresMode
Indicates that one entity operates in, supports, or is characterized by a particular mode or configuration specified by another entity.
-
E.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 22, 2026, 8:26 a.m.