Triple
T36254375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoebe |
E891892
|
entity |
| Predicate | passedOnDomainTo |
P185066
|
FINISHED |
| Object | Apollo |
—
|
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: Apollo | Statement: [Phoebe, passedOnDomainTo, Apollo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passedOnDomainTo Context triple: [Phoebe, passedOnDomainTo, Apollo]
-
A.
dedicatedToDomain
Indicates that something is specifically designed, intended, or reserved for use within a particular domain or area of application.
-
B.
affectedDomain
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
C.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
D.
portedTo
Indicates that something has been adapted or transferred from its original environment or platform to run or function on a different one.
-
E.
replacedInDomain
Indicates that one entity has been superseded or substituted by another within a specific domain or contextual scope.
- F. None of above. chosen
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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.