Triple
T1859490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G3-b |
E41781
|
entity |
| Predicate | likelyFunction |
P14769
|
FINISHED |
| Object | queens pyramid |
—
|
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: queens pyramid | Statement: [G3-b, likelyFunction, queens pyramid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyFunction Context triple: [G3-b, likelyFunction, queens pyramid]
-
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.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
C.
functionHypothesis
chosen
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
D.
hasTendency
Indicates that an entity is inclined or likely to exhibit a particular behavior, characteristic, or outcome under certain conditions.
-
E.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.