Triple
T29434766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Explorers |
E746537
|
entity |
| Predicate | featuresEarlyRoleFor |
P192274
|
FINISHED |
| Object | River Phoenix |
—
|
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: River Phoenix | Statement: [Explorers, featuresEarlyRoleFor, River Phoenix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresEarlyRoleFor Context triple: [Explorers, featuresEarlyRoleFor, River Phoenix]
-
A.
featuresEarlyProminentRoleFor
chosen
Indicates that something includes another entity in an early and prominently visible or important role.
-
B.
featuresEarlyVersionOf
Indicates that something includes or presents an earlier or preliminary version of another thing.
-
C.
featuresEarlyAppearanceBy
Indicates that something prominently includes or showcases an entity at an early stage or initial part of its sequence, timeline, or presentation.
-
D.
earlyRole
Indicates that an entity held a particular role or position during an early or initial stage of its involvement or development.
-
E.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: April 28, 2026, 3:15 p.m.