Triple
T1468561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caproni Ca.135 |
E27080
|
entity |
| Predicate | sawLimitedService |
P24723
|
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: [Caproni Ca.135, sawLimitedService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawLimitedService Context triple: [Caproni Ca.135, sawLimitedService, true]
-
A.
hasLimitedParticipation
chosen
Indicates that an entity is involved in an activity, event, or process only to a restricted or constrained extent, rather than with full participation.
-
B.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
C.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5d70a948190b50a6c1b36abc740 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.