Triple
T17610369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTF |
E428949
|
entity |
| Predicate | testArticleType |
P6001
|
FINISHED |
| Object | scaled aircraft models |
—
|
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: scaled aircraft models | Statement: [NTF, testArticleType, scaled aircraft models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testArticleType Context triple: [NTF, testArticleType, scaled aircraft models]
-
A.
articleType
chosen
Indicates the specific category or kind of article associated with an entity.
-
B.
typicalArticle
Indicates that one entity is a standard, representative, or commonly occurring instance of the type or category denoted by the other entity.
-
C.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
-
D.
containsArticle
Indicates that one entity includes or holds an article (such as a written piece, item, or document) as part of its contents.
-
E.
implementsArticle
Indicates that one entity carries out, realizes, or puts into practice the content, requirements, or provisions specified by a particular article.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2d294881908380b2ab0b4d2503 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.