Triple
T30057946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headquarters (Riley's mind) |
E763785
|
entity |
| Predicate | belongsToCharacter |
P195494
|
FINISHED |
| Object | Riley Andersen |
—
|
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: Riley Andersen | Statement: [Headquarters (Riley's mind), belongsToCharacter, Riley Andersen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCharacter Context triple: [Headquarters (Riley's mind), belongsToCharacter, Riley Andersen]
-
A.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
-
B.
propertyOnCharacters
Indicates that a certain property or attribute is associated with one or more characters.
-
C.
givenByCharacter
Indicates that something (such as an item, information, or assistance) is provided or handed over by a particular character.
-
D.
usedByCharacterFor
Indicates that something is utilized or employed by a character for a particular purpose or function.
-
E.
associatedWithCharacterFamily
Indicates a relationship where something is linked or connected to a particular character’s family.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: April 29, 2026, 6:57 p.m.