Triple
T32759461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | @candiceswanepoel |
E837714
|
entity |
| Predicate | hasBio |
P180275
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [@candiceswanepoel, hasBio, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBio Context triple: [@candiceswanepoel, hasBio, yes]
-
A.
hasBiologicalComponents
Indicates that an entity is composed of, contains, or is associated with one or more biological parts or substances.
-
B.
hasBiologicalBasisIn
Indicates that one entity is grounded in, caused by, or dependent on the biological properties, processes, or mechanisms of another entity.
-
C.
hasOrganism
Indicates that one entity is an organism associated with, contained in, or otherwise possessed by another entity.
-
D.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
E.
hasBiologicalRelevance
Indicates that something is pertinent to, affects, or is meaningfully connected with biological processes, systems, or functions.
- F. None of above. chosen
Provenance (4 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: May 1, 2026, 1:13 a.m.