Triple
T27584546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Objectory AB |
E699659
|
entity |
| Predicate | methodIntegratedInto |
P15157
|
FINISHED |
| Object | Rational Unified Process |
—
|
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: Rational Unified Process | Statement: [Objectory AB, methodIntegratedInto, Rational Unified Process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodIntegratedInto Context triple: [Objectory AB, methodIntegratedInto, Rational Unified Process]
-
A.
mayBeIntegratedWith
Indicates that one entity has the potential or capability to be combined or incorporated with another entity into a unified or interoperable whole.
-
B.
integratedIn
chosen
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
-
C.
previouslyIntegratedInto
Indicates that an entity was formerly incorporated or included as part of another entity or system in the past.
-
D.
integratedFrom
Indicates that something has been formed or constructed by combining or incorporating elements originating from another source.
-
E.
implementedAsPartOf
Indicates that something has been realized or carried out as a component or subset of a larger implementation or project.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:03 p.m.