Triple
T25516179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Screaming Eagle shoulder sleeve insignia |
E639513
|
entity |
| Predicate | hasMottoOnScroll |
P141177
|
FINISHED |
| Object | AIRBORNE |
—
|
NE NERFINISHED |
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: AIRBORNE | Statement: [Screaming Eagle shoulder sleeve insignia, hasMottoOnScroll, AIRBORNE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOnScroll Context triple: [Screaming Eagle shoulder sleeve insignia, hasMottoOnScroll, AIRBORNE]
-
A.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoScript
Indicates that an entity’s motto is written or expressed in a particular writing system or script.
-
C.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
D.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
E.
mottoIncluded
chosen
Indicates that a motto is present as part of, or associated with, the referenced 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 21, 2026, 2:56 p.m.