Triple
T25639226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leof |
E642789
|
entity |
| Predicate | functionInNames |
P159787
|
FINISHED |
| Object | expresses endearment toward the named person |
—
|
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: expresses endearment toward the named person | Statement: [Leof, functionInNames, expresses endearment toward the named person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInNames Context triple: [Leof, functionInNames, expresses endearment toward the named person]
-
A.
functionInName
Indicates that the name of one entity includes or references the function or role of another entity.
-
B.
namingFunction
Indicates a relationship where one entity serves as the name or naming mechanism assigned to another entity.
-
C.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
D.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
E.
functionInStructure
Indicates that one entity serves as a functional component or plays a specific operational role within the organization or structure of another entity.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa64332081909df65f8b4380f152 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 5:38 p.m.