Triple
T33028310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenLDAP Public License |
E845098
|
entity |
| Predicate | hasOriginProject |
P175836
|
FINISHED |
| Object | OpenLDAP |
—
|
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: OpenLDAP | Statement: [OpenLDAP Public License, hasOriginProject, OpenLDAP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginProject Context triple: [OpenLDAP Public License, hasOriginProject, OpenLDAP]
-
A.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
B.
isFromProject
chosen
Indicates that one entity originates from, belongs to, or was produced within a particular project.
-
C.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
D.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
E.
hasPlanningOrigin
Indicates that something originates from, or is derived from, a particular planning process, plan, or planning 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 1, 2026, 1:23 a.m.