Triple
T31910449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac Conmara |
E814665
|
entity |
| Predicate | meaningOfElement_mac |
P162738
|
FINISHED |
| Object | son of |
—
|
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 of | Statement: [Mac Conmara, meaningOfElement_mac, son of]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfElement_mac Context triple: [Mac Conmara, meaningOfElement_mac, son of]
-
A.
macMeaning
chosen
Indicates that one entity specifies or conveys the meaning or semantic interpretation of another entity within a mac-related context (e.g., a term, code, or identifier).
-
B.
deviceMeaning
Indicates that one entity specifies or conveys the functional meaning, purpose, or interpretation of a device-related entity.
-
C.
nodeMeaning
Indicates that one entity represents, defines, or conveys the semantic content or intended meaning of another entity.
-
D.
FitzElementMeaning
Indicates a relationship where an element is associated with, or conveys, a particular meaning or interpretive significance.
-
E.
definesMAC
Indicates that one entity specifies or establishes the Media Access Control (MAC) address or MAC-related configuration for another entity.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:01 a.m.