Triple
T34415949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negation |
E883403
|
entity |
| Predicate | hasArity |
P127965
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Negation, hasArity, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArity Context triple: [Negation, hasArity, 1]
-
A.
hasConstraintArity
Indicates that a constraint is associated with a specific number of arguments or elements it applies to.
-
B.
argumentCount
chosen
Indicates the number of arguments that a function, method, or callable entity takes.
-
C.
hasArgumentType
Indicates that an argument or parameter in a function, method, or relation is of a specified data type or class.
-
D.
hasArgument
Indicates that one entity serves as an argument (such as an input, parameter, or participant) in relation to another entity, typically a function, event, or statement.
-
E.
hasOverload
Indicates that an entity defines multiple variants (overloads) of the same operation or function, typically distinguished by differing parameters or signatures.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 1:59 a.m.