Triple
T33095031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPIN |
E846885
|
entity |
| Predicate | supportsPropertySpecification |
P5374
|
FINISHED |
| Object | LTL |
E824076
|
NE 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: LTL | Statement: [SPIN, supportsPropertySpecification, LTL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPropertySpecification Context triple: [SPIN, supportsPropertySpecification, LTL]
-
A.
supportsProp
Indicates that one entity provides assistance, endorsement, or backing for a particular property, attribute, or characteristic of another entity.
-
B.
hasSpecification
chosen
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
C.
supportsSpecificationVersion
Indicates that one entity is compatible with and able to operate according to a particular version of a specification.
-
D.
requiresProperty
Indicates that one entity depends on another entity possessing a specific property or attribute in order for a condition, action, or relationship to hold.
-
E.
canHaveProperty
Indicates that an entity is capable of possessing or being assigned a particular property.
- F. None of above.
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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f02b316481909ba457919ef0d8c7 |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.