Triple
T23416588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iacobus Minor |
E560523
|
entity |
| Predicate | hasTraditionalAttribute |
P133748
|
FINISHED |
| Object | fuller's club |
—
|
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: fuller's club | Statement: [Iacobus Minor, hasTraditionalAttribute, fuller's club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalAttribute Context triple: [Iacobus Minor, hasTraditionalAttribute, fuller's club]
-
A.
hasTraditionalFeatures
chosen
Indicates that something possesses characteristics or attributes commonly associated with established traditions or customary practices.
-
B.
hasTraditionElement
Indicates that something includes, embodies, or is associated with a particular traditional practice, custom, or cultural element.
-
C.
hasTraditionalBase
Indicates that something is supported by, built upon, or derived from an established traditional foundation or practice.
-
D.
hasTraditionalValue
Indicates that something embodies, reflects, or is associated with long-established customs, norms, or cultural values.
-
E.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a515fe048190adefdefaeff76cfd |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.