Triple
T10168242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noise_NK pattern |
E235260
|
entity |
| Predicate | authenticatesParty |
P92200
|
FINISHED |
| Object | responder only |
—
|
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: responder only | Statement: [Noise_NK pattern, authenticatesParty, responder only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authenticatesParty Context triple: [Noise_NK pattern, authenticatesParty, responder only]
-
A.
recognizesParty
Indicates that one entity formally acknowledges the existence, status, or legitimacy of another party.
-
B.
signerParty
Indicates the party that formally signs or executes a document, agreement, or instrument.
-
C.
determinesParticipantIn
Indicates that one entity has the authority or role to decide or specify which other entity (or entities) will participate in a given event, activity, or process.
-
D.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
E.
keyParty
Indicates a relationship where an entity is a primary or essential participant in an event, agreement, or situation.
- F. None of above. chosen
Provenance (4 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6f64a48190883aefce58a65ca6 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.