Triple
T33048867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flamines |
E845669
|
entity |
| Predicate | requiredCompanion |
P167046
|
FINISHED |
| Object | wife in some rituals |
—
|
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: wife in some rituals | Statement: [flamines, requiredCompanion, wife in some rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredCompanion Context triple: [flamines, requiredCompanion, wife in some rituals]
-
A.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
B.
requiresComplement
Indicates that one entity depends on another entity as a necessary complement to be complete, functional, or valid.
-
C.
supportsCompanion
Indicates that one entity provides assistance, encouragement, or backing to another entity in a companion or partner role.
-
D.
requiresAccompaniment
chosen
Indicates that one entity must be accompanied or attended by another entity in order for an action, event, or condition to occur or be valid.
-
E.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 1, 2026, 1:24 a.m.