Triple
T27607063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mac Echdach |
E700209
|
entity |
| Predicate | macMeaning |
P162738
|
FINISHED |
| Object | son |
—
|
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: son | Statement: [mac Echdach, macMeaning, son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: macMeaning Context triple: [mac Echdach, macMeaning, son]
-
A.
deviceMeaning
Indicates that one entity specifies or conveys the functional meaning, purpose, or interpretation of a device-related entity.
-
B.
apMeaning
Indicates that one entity expresses, conveys, or signifies the meaning or semantic content of another entity.
-
C.
nodeMeaning
Indicates that one entity represents, defines, or conveys the semantic content or intended meaning of another entity.
-
D.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
E.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6309ccc488190a068cedfc5d740fd |
completed | May 2, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:10 p.m.