Triple
T4443754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erlang |
E96230
|
entity |
| Predicate | openSourcedIn |
P7052
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Erlang, openSourcedIn, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openSourcedIn Context triple: [Erlang, openSourcedIn, 1998]
-
A.
openSourceProject
Indicates that the subject is a software project whose source code is publicly available and can be used, modified, and redistributed under an open-source license.
-
B.
openSource
chosen
Indicates that the subject makes its source code publicly available under a license that allows others to use, modify, and redistribute it.
-
C.
openSourceAttempt
Indicates an attempt or effort by an entity to make something open source, such as releasing code or resources under an open-source license.
-
D.
sourceCodeReleasedBy
Indicates that the source code of a software or project has been made publicly available by a specific releasing entity.
-
E.
supportsOpenSource
Indicates that one entity actively endorses, contributes to, or otherwise promotes open-source software or open-source initiatives.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355b052688190a0d8e5912f82151c |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.