Triple
T10384824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Golden Girl |
E244733
|
entity |
| Predicate | appliedToField |
P89856
|
FINISHED |
| Object | track and field |
—
|
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: track and field | Statement: [The Golden Girl, appliedToField, track and field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToField Context triple: [The Golden Girl, appliedToField, track and field]
-
A.
appliesField
chosen
Indicates that a particular field, attribute, or property is used or applied to an entity within a given context or operation.
-
B.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
C.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
D.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
E.
appliedToEntityType
Indicates that something (such as a rule, constraint, or operation) is specifically applied to entities of a given type.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a35fb08190ab85b4a8f8dea511 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.