Triple
T4760994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gideon |
E105695
|
entity |
| Predicate | performedSign |
P12381
|
FINISHED |
| Object | fleece wet and ground dry |
—
|
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: fleece wet and ground dry | Statement: [Gideon, performedSign, fleece wet and ground dry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedSign Context triple: [Gideon, performedSign, fleece wet and ground dry]
-
A.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
B.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
C.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
hasSignFor
chosen
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
E.
performedImpressionOf
Indicates that one entity imitated or mimicked another entity, typically reproducing their voice, mannerisms, or style as a performance.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.