Triple
T23046355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tools for Humanity |
E573886
|
entity |
| Predicate | roleInWorldcoin |
P150777
|
FINISHED |
| Object | core developer |
—
|
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: core developer | Statement: [Tools for Humanity, roleInWorldcoin, core developer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWorldcoin Context triple: [Tools for Humanity, roleInWorldcoin, core developer]
-
A.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
B.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
-
C.
roleInCosmos
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
D.
roleAtThePlanet
Indicates that an entity holds or performs a specific role or function at, on, or for a particular planet.
-
E.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185192754819093a87d23371e7bbc |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:54 p.m.