Triple
T11758137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirk (surname element) |
E279581
|
entity |
| Predicate | typicalFunctionInSurname |
P101208
|
FINISHED |
| Object | locative indicator |
—
|
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: locative indicator | Statement: [Kirk (surname element), typicalFunctionInSurname, locative indicator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFunctionInSurname Context triple: [Kirk (surname element), typicalFunctionInSurname, locative indicator]
-
A.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
B.
hasExampleSurname
Indicates that an entity is associated with a sample or illustrative surname used as an example rather than a real or primary family name.
-
C.
typicalFullName
Indicates that the object is the standard or commonly used full name associated with the subject.
-
D.
familyName
Indicates that one entity is the family (last) name associated with another entity (typically a person).
-
E.
functionInName
Indicates that the name of one entity includes or references the function or role 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5220f148190ae60d1941a579ab6 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890467a2481909ce6c669e739c8de |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.