Triple
T6665597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memphite Triad |
E151592
|
entity |
| Predicate | hasPatronFunction |
P45407
|
FINISHED |
| Object | patron of craftsmen |
—
|
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: patron of craftsmen | Statement: [Memphite Triad, hasPatronFunction, patron of craftsmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronFunction Context triple: [Memphite Triad, hasPatronFunction, patron of craftsmen]
-
A.
usedAsPatronOf
Indicates that one entity serves as a patron or sponsor for another, providing support, endorsement, or backing.
-
B.
hasPatronageOver
chosen
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
-
C.
hasNotablePatron
Indicates that an entity is significantly supported, sponsored, or championed by a distinguished or influential patron.
-
D.
hasFormerPatron
Indicates that an entity previously served as a patron or sponsor of another entity, but no longer holds that role.
-
E.
hasPierFunction
Indicates that an entity serves the role or function of a pier, such as providing a structure that extends over water for access, docking, or related activities.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.