Triple
T7423292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDF 1.1 N-Quads |
E171300
|
entity |
| Predicate | statementArity |
P21071
|
FINISHED |
| Object | four-part statements |
—
|
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: four-part statements | Statement: [RDF 1.1 N-Quads, statementArity, four-part statements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statementArity Context triple: [RDF 1.1 N-Quads, statementArity, four-part statements]
-
A.
argumentType
Indicates that one entity serves as a specific semantic or syntactic argument role (such as subject, object, or complement) in relation to another entity or event.
-
B.
parameterCount
chosen
Indicates the number of parameters associated with a given function, method, or callable entity.
-
C.
quantifiesOver
Indicates that one entity expresses a quantity, measurement, or numerical specification that applies to or ranges over another entity.
-
D.
clauseNumber
Indicates the specific numbered position or identifier assigned to a clause within a larger document or agreement.
-
E.
statement
Indicates that an entity makes, issues, or expresses a declarative assertion, claim, or remark about something.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2eece588190905774e7151edcb8 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.