Triple
T36932954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noblac |
E913532
|
entity |
| Predicate | hasNameInTradition |
P17611
|
FINISHED |
| Object | Noblac |
—
|
NE NERFINISHED |
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: Noblac | Statement: [Noblac, hasNameInTradition, Noblac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInTradition Context triple: [Noblac, hasNameInTradition, Noblac]
-
A.
hasTraditionalName
chosen
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
B.
belongsToNamingTradition
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
C.
hasUseInTradition
Indicates that something is employed or holds a functional role within a particular cultural, religious, or historical tradition.
-
D.
mentionedInTraditionOf
Indicates that something is referenced, recognized, or discussed within the body of beliefs, practices, or narratives of a particular tradition.
-
E.
textBelongsToTradition
Indicates that a given text is associated with, derived from, or recognized as part of a particular intellectual, cultural, or religious tradition.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:13 p.m.