Triple
T34161122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oreads |
E876279
|
entity |
| Predicate | oftenCompanionsOf |
P2932
|
FINISHED |
| Object | Artemis |
—
|
NE NERFINISHED |
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: Artemis | Statement: [Oreads, oftenCompanionsOf, Artemis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCompanionsOf Context triple: [Oreads, oftenCompanionsOf, Artemis]
-
A.
wasCompanionOf
chosen
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
B.
allegedCompanions
Indicates that two or more entities are claimed or reported to have been companions or associates, without confirming the truth of that relationship.
-
C.
hasNumberOfCompanions
Indicates the quantity of companions or associates that an entity has.
-
D.
companionsCategory
Indicates that one entity is classified under a specific category related to companions or companionship.
-
E.
hasFictionalCompanion
Indicates that one entity has another entity as its fictional companion, typically within a narrative or imaginative context.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:54 a.m.