Triple
T26509266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in France |
E669632
|
entity |
| Predicate | collaborationLeader |
P68732
|
FINISHED |
| Object | Pierre Laval |
—
|
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: Pierre Laval | Statement: [Holocaust in France, collaborationLeader, Pierre Laval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationLeader Context triple: [Holocaust in France, collaborationLeader, Pierre Laval]
-
A.
collaborationLedBy
chosen
Indicates that a collaborative effort or project is directed, coordinated, or overseen by a specific leading entity.
-
B.
coLeaderWith
Indicates that two or more entities share a joint leadership role or position with equal or comparable authority.
-
C.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
D.
coLeadOf
Indicates a relationship where two or more entities share joint leadership responsibility over the same project, group, or initiative.
-
E.
designatedLeader
Indicates that one entity has been formally chosen or assigned to serve as the leader of another entity or group.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:19 a.m.