Triple
T7970080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resistance |
E185300
|
entity |
| Predicate | notableMember |
P10
|
FINISHED |
| Object | Finn |
E74813
|
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: Finn | Statement: [Resistance, notableMember, Finn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Finn Context triple: [Resistance, notableMember, Finn]
-
A.
Finn
chosen
Finn is a central character in the Star Wars sequel trilogy, a former stormtrooper who defects from the First Order and joins the Resistance.
-
B.
Finn
Finn is a masculine given name of Old Norse and Irish origin, commonly used in Scandinavian and English-speaking countries.
-
C.
Finn the Human
Finn the Human is the brave, adventurous boy hero and primary protagonist of the animated television series Adventure Time.
-
D.
Olaf
Olaf is a masculine given name of Old Norse origin, commonly used in Germanic and Scandinavian countries.
-
E.
Fynn
Fynn is an alternative spelling of the given name Finn, used as a modern variant in various European languages.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd304dc8190b9feee5e17fc66db |
completed | March 31, 2026, 3:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc56710dd0819084da3898cb0933b0 |
completed | March 31, 2026, 11:19 p.m. |
Created at: March 30, 2026, 5:13 p.m.