Triple
T3428970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heritage |
E72291
|
entity |
| Predicate | complicationAvailability |
P13910
|
FINISHED |
| Object | time-only models |
—
|
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: time-only models | Statement: [Heritage, complicationAvailability, time-only models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complicationAvailability Context triple: [Heritage, complicationAvailability, time-only models]
-
A.
hasComplication
Indicates that an entity is associated with a problem, difficulty, or adverse outcome arising as a consequence of another condition, action, or process.
-
B.
complication
Indicates that one event, action, or condition makes another more difficult, problematic, or introduces an additional obstacle or entanglement in the situation.
-
C.
availableWith
chosen
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
D.
hasIndication
Indicates that one entity (typically a product, treatment, or intervention) is intended, approved, or suitable for use in addressing, preventing, or managing a particular condition, purpose, or circumstance.
-
E.
connectivityFeatures
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
- F. None of above.
Provenance (3 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9854ca081909e637adcac46a27c |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.