Triple
T29900792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lazarus |
E759401
|
entity |
| Predicate | usesComponentLibrary |
P55160
|
FINISHED |
| Object | Lazarus Component Library |
—
|
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: Lazarus Component Library | Statement: [Lazarus, usesComponentLibrary, Lazarus Component Library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesComponentLibrary Context triple: [Lazarus, usesComponentLibrary, Lazarus Component Library]
-
A.
usedComponent
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
B.
usesArchitectureComponent
Indicates that one entity employs or incorporates a specific architecture component as part of its structure, design, or implementation.
-
C.
componentIncluded
Indicates that one entity is a constituent part or subcomponent that is contained within or included in another entity.
-
D.
usedInLibrary
Indicates that something is utilized or applied within the context of a library, such as a software library or a physical library system.
-
E.
implementedInLibrary
chosen
Indicates that a particular functionality, feature, or component is realized and provided within a specific software library.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 6:06 p.m.