Triple
T16623321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legends of Tomorrow |
E403883
|
entity |
| Predicate | spinOffFrom |
P7226
|
FINISHED |
| Object | Arrow |
E149849
|
NE 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: Arrow | Statement: [Legends of Tomorrow, spinOffFrom, Arrow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arrow Context triple: [Legends of Tomorrow, spinOffFrom, Arrow]
-
A.
Arrow
Arrow is the English translation of "Freccia," the nickname of the Italian World War II fighter aircraft Fiat G.50.
-
B.
Arrow
chosen
Arrow is a popular American superhero television series based on the DC Comics character Green Arrow, known for launching the interconnected "Arrowverse" franchise.
-
C.
Arrow
Arrow is a common English surname borne by various individuals, including the influential economist Kenneth Arrow.
-
D.
Arrow
Arrow is a regional passenger rail service brand used for trains operating between San Bernardino and Redlands in Southern California.
-
E.
Arrow
Arrow is a long-established American clothing brand best known for its men’s dress shirts and formalwear.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754f4f508190a5b4b8511623fcd4 |
completed | April 18, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a50bcbe88190a424a361ee885b0c |
completed | May 10, 2026, 3:32 p.m. |
Created at: April 10, 2026, 5:17 a.m.