Triple
T33413579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDAPBIS |
E855652
|
entity |
| Predicate | focusesOnAcronym |
P141478
|
FINISHED |
| Object | LDAP |
—
|
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: LDAP | Statement: [LDAPBIS, focusesOnAcronym, LDAP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnAcronym Context triple: [LDAPBIS, focusesOnAcronym, LDAP]
-
A.
acronymContext
chosen
Indicates that one term is used as an acronym specifically within the contextual scope defined by another entity (such as a document, domain, or usage setting).
-
B.
acronymExpansion
Indicates that one term is an acronym whose letters stand for the words in another, longer expression.
-
C.
processedByAcronym
Indicates that something has been processed or handled by an entity identified by its acronym.
-
D.
abbreviationRefersTo
Indicates that an abbreviation stands for or denotes the full form or concept it is associated with.
-
E.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:36 a.m.