Triple
T8317719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Norman |
E194747
|
entity |
| Predicate | influenced |
P9
|
FINISHED |
| Object | Picard |
E349035
|
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: Picard | Statement: [Old Norman, influenced, Picard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Picard Context triple: [Old Norman, influenced, Picard]
-
A.
Picard
chosen
Picard is a Romance language closely related to French, traditionally spoken in parts of northern France and southern Belgium.
-
B.
Jean-Luc Picard
Jean-Luc Picard is the thoughtful and principled Starfleet captain of the USS Enterprise in the Star Trek franchise, known for his diplomacy, intellect, and moral leadership.
-
C.
Riker
Riker is a surname most prominently associated with the American Riker family, including historical figures in New York such as Abraham Rycken.
-
D.
Will Riker
Will Riker is a charismatic Starfleet officer best known as Captain Jean-Luc Picard’s trusted first officer aboard the USS Enterprise in the Star Trek franchise.
-
E.
Geordi La Forge
Geordi La Forge is a key Starfleet engineer in the Star Trek universe, best known as the visually impaired chief engineer of the USS Enterprise-D who uses a VISOR to see.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f630ea881909fb639383e60aee9 |
completed | March 31, 2026, 8:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd958cf0808190af59e36c35b91e58 |
completed | April 1, 2026, 10 p.m. |
Created at: March 30, 2026, 5:55 p.m.