Triple
T6438500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Runner |
E129958
|
entity |
| Predicate | positionIsRecordedAs |
P48371
|
FINISHED |
| Object | R on some scorecards |
—
|
LITERAL FINISHED |
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: R on some scorecards | Statement: [The Runner, positionIsRecordedAs, R on some scorecards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionIsRecordedAs Context triple: [The Runner, positionIsRecordedAs, R on some scorecards]
-
A.
positionMayBeKnownAs
chosen
Indicates that a particular position or role can be referred to by an alternative name or title.
-
B.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
-
C.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
D.
positionObtainedBy
Indicates that a particular position or role is acquired, achieved, or secured through a specified action, process, or agent.
-
E.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06965a5d48190a5860da9e22dc6e0 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:45 p.m.