Triple
T29443829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSEC3PARAM |
E746789
|
entity |
| Predicate | mustBeSigned |
P167186
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NSEC3PARAM, mustBeSigned, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustBeSigned Context triple: [NSEC3PARAM, mustBeSigned, true]
-
A.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
B.
mayBeSignedAs
Indicates that one entity can optionally be used or recognized as the signature or signed form of another entity.
-
C.
haveSigned
Indicates that an entity has completed and formally agreed to a document, contract, or agreement by signing it.
-
D.
membershipRequired
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
-
E.
mustServe
Indicates that one entity is obligated or required to provide service or perform duties for another entity.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b1f46cc8190aeed9e77976f5cd1 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:25 p.m.