Triple
T7984791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache Spark |
E185661
|
entity |
| Predicate | topLevelProjectSince |
P36578
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Apache Spark, topLevelProjectSince, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelProjectSince Context triple: [Apache Spark, topLevelProjectSince, 2014]
-
A.
parentProject
Indicates that one project serves as the direct higher-level or containing project in relation to another project.
-
B.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
C.
developedSince
chosen
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
D.
latestVersionYear
Indicates the calendar year in which the most recent version of an entity (such as a product, document, or software) was released or became available.
-
E.
hasProject
Indicates that an entity is associated with or responsible for a particular 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4a55b881909a96133e56c0dffa |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.