Triple
T20147432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S II |
E491339
|
entity |
| Predicate | hasTransitionType |
P138850
|
FINISHED |
| Object | forbidden line |
—
|
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: forbidden line | Statement: [S II, hasTransitionType, forbidden line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransitionType Context triple: [S II, hasTransitionType, forbidden line]
-
A.
hasTransformationType
Indicates that an entity undergoes or is associated with a specific kind or category of transformation.
-
B.
hasMoveType
Indicates that an action or move is associated with a specific type or category (such as elemental, functional, or classification-based).
-
C.
isTransitionalBetween
Indicates that something serves as an intermediate or bridging state, form, or phase between two other distinct states, forms, or phases.
-
D.
hasTransitionUpperLevel
Indicates a relationship where something possesses or is associated with an upper-level transition state or phase within a hierarchical or multi-level process.
-
E.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679f43bc8190a1cd4768b3e87505 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:33 p.m.