Triple
T14936677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Var |
E372411
|
entity |
| Predicate | hasLimitedAttestation |
P116736
|
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: [Var, hasLimitedAttestation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedAttestation Context triple: [Var, hasLimitedAttestation, true]
-
A.
hasAttestation
Indicates that there exists a formal confirmation, evidence, or certification supporting the validity or authenticity of something.
-
B.
hasApproximateNumberOfAttestedWords
Indicates that an entity is associated with an estimated or approximate count of words that are documented or attested for it.
-
C.
hasLimitedAuthorityOver
Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
-
D.
hasEndorser
Indicates that one entity supports, approves, or publicly backs another entity, typically lending it credibility or validation.
-
E.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded647ae388190a0e97c03f2a4d832 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:37 a.m.