Triple
T30932307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paddy |
E788026
|
entity |
| Predicate | hasMeaningViaPatrick |
P195730
|
FINISHED |
| Object | nobleman |
—
|
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: nobleman | Statement: [Paddy, hasMeaningViaPatrick, nobleman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningViaPatrick Context triple: [Paddy, hasMeaningViaPatrick, nobleman]
-
A.
hasMeaningViaJohn
Indicates that something possesses or conveys its meaning specifically through John as the interpretive or mediating agent.
-
B.
hasMeaningViaAlice
Indicates that something possesses or conveys its meaning specifically through Alice as the mediating agent or interpretive source.
-
C.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
D.
hasMeaningByDerivation
Indicates that the meaning of one entity is obtained or derived from another entity, rather than being original or independent.
-
E.
hasMultipleMeanings
Indicates that a term, symbol, or expression is associated with more than one distinct meaning or 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: April 29, 2026, 8:52 p.m.