Triple
T597316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boaz and Jachin |
E11414
|
entity |
| Predicate | haveFunction |
P182
|
FINISHED |
| Object | monumental entrance markers |
—
|
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: monumental entrance markers | Statement: [Boaz and Jachin, haveFunction, monumental entrance markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveFunction Context triple: [Boaz and Jachin, haveFunction, monumental entrance markers]
-
A.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
B.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
C.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
hasTransportFunction
Indicates that an entity serves to move or carry something (such as people, goods, or signals) from one place or state to another.
-
E.
hasReserveFunction
Indicates that an entity serves as a backup or secondary option that can perform the same function if the primary one is unavailable or fails.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49dc4f7d08190990f70b9b3af6ce5 |
completed | March 1, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69a49cf59cd0819084e67981cb371e25 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.