Triple
T5581550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgo |
E146650
|
entity |
| Predicate | associatedElementTraits |
P53226
|
FINISHED |
| Object | practicality |
—
|
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: practicality | Statement: [Virgo, associatedElementTraits, practicality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedElementTraits Context triple: [Virgo, associatedElementTraits, practicality]
-
A.
associatedWithElement
Indicates a relationship where one entity is linked or connected to a particular element, such that the element is relevant to, involved in, or characteristic of that entity.
-
B.
elementalAssociation
chosen
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
-
C.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
D.
associatedValue
Indicates that one entity is linked to another entity that serves as its corresponding or contextually related value.
-
E.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208147a48190b2cdb42b9c9814a3 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.