Triple
T25319999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outer space (Culler–Vogtmann Outer space) |
E634850
|
entity |
| Predicate | hasActionBy |
P16860
|
FINISHED |
| Object | Out(F_n) |
—
|
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: Out(F_n) | Statement: [Outer space (Culler–Vogtmann Outer space), hasActionBy, Out(F_n)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActionBy Context triple: [Outer space (Culler–Vogtmann Outer space), hasActionBy, Out(F_n)]
-
A.
hasActionType
Indicates that an action or event is classified as belonging to a specific type or category of actions.
-
B.
hasOwnerAction
Indicates that an owner performs, initiates, or is responsible for a specific action related to the owned entity.
-
C.
hasActs
Indicates that an entity is associated with one or more actions, performances, or deeds it carries out or is responsible for.
-
D.
hasAct
chosen
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
E.
hasPageAction
Indicates that a specific action or operation is associated with, or can be performed on, a particular page.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 1:28 p.m.