Triple
T14343288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akka |
E355653
|
entity |
| Predicate | followsSpecification |
P25860
|
FINISHED |
| Object | Reactive Manifesto principles |
—
|
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: Reactive Manifesto principles | Statement: [Akka, followsSpecification, Reactive Manifesto principles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSpecification Context triple: [Akka, followsSpecification, Reactive Manifesto principles]
-
A.
hasSpecification
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
meetsFollowing
Indicates that one entity encounters or comes together with another entity that appears or occurs later in a given sequence or order.
-
C.
followsRubricsOf
chosen
Indicates that one entity adheres to, complies with, or operates according to the rules, guidelines, or evaluation criteria defined by another entity.
-
D.
relatedToSpecification
Indicates that something has a connection or relevance to a particular specification, standard, or set of defined requirements.
-
E.
followsPass
Indicates that one entity moves behind or in the path of another entity who has just passed, maintaining a trailing or subsequent position.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e89ed9c8190acdb647ee618e919 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.