Triple
T17340232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Day for Night |
E421046
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Ferrand |
E292535
|
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: Ferrand | Statement: [Day for Night, featuresCharacter, Ferrand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ferrand Context triple: [Day for Night, featuresCharacter, Ferrand]
-
A.
Ferrand
chosen
Ferrand is a given name and surname of French origin, related to the name Ferdinand.
-
B.
Courcier
Courcier was a French publishing house known for issuing important mathematical and scientific works in the early 19th century.
-
C.
Boucicaut
Boucicaut is a station on the Paris Métro serving the 15th arrondissement of Paris.
-
D.
Guérard
Guérard is a small commune in the Seine-et-Marne department in north-central France, known for its rural character and proximity to the Paris metropolitan area.
-
E.
Guerin
Guerin is a surname of French origin borne by various notable individuals across fields such as arts, sports, and public life.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a14ec90819098db2ac0d58a53e1 |
completed | April 19, 2026, 2:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c588a7081909ab108cb4adfedfe |
completed | May 11, 2026, 7:59 a.m. |
Created at: April 10, 2026, 5:44 a.m.