Triple
T24930446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armand David |
E618968
|
entity |
| Predicate | sentSpecimensTo |
P64532
|
FINISHED |
| Object | Muséum national d'Histoire naturelle |
—
|
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: Muséum national d'Histoire naturelle | Statement: [Armand David, sentSpecimensTo, Muséum national d'Histoire naturelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentSpecimensTo Context triple: [Armand David, sentSpecimensTo, Muséum national d'Histoire naturelle]
-
A.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
B.
sentMembersTo
Indicates that one entity dispatched or assigned its members to another entity or location.
-
C.
sends
chosen
Indicates that one entity transmits or dispatches something (such as a message, object, or signal) to another entity.
-
D.
collectedSpecimensFor
Indicates that one entity gathered or obtained specimens on behalf of or for the benefit of another entity.
-
E.
collectedSpecimensIn
Indicates that an entity gathered or obtained specimens within a specified location or context.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f423b3b3408190bd586454c2cf9be7 |
completed | May 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:29 a.m.