Triple
T11041950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guaiacum sanctum |
E261038
|
entity |
| Predicate | resinName |
P744
|
FINISHED |
| Object | guaiacum resin |
—
|
LITERAL 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: guaiacum resin | Statement: [Guaiacum sanctum, resinName, guaiacum resin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resinName Context triple: [Guaiacum sanctum, resinName, guaiacum resin]
-
A.
nameOf
chosen
Indicates that one entity is the name or designation of another entity.
-
B.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
-
C.
reserveName
Indicates that an entity secures or sets aside a specific name so that it cannot be used by others.
-
D.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
E.
remnantName
Indicates that an entity is identified by a name specifically associated with a remaining part, leftover, or surviving fragment of something previously whole.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7980134c8819098122d83380a1f79 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.