Triple
T2313734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harald Welte |
E51014
|
entity |
| Predicate | hasAdvocatedFor |
P33
|
FINISHED |
| Object | compliance with the GNU General Public License |
—
|
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: compliance with the GNU General Public License | Statement: [Harald Welte, hasAdvocatedFor, compliance with the GNU General Public License]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdvocatedFor Context triple: [Harald Welte, hasAdvocatedFor, compliance with the GNU General Public License]
-
A.
advocates
chosen
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
B.
hasAdvocacyMethod
Indicates the method, strategy, or approach used to advocate for a cause, issue, or entity.
-
C.
advocatesAgainst
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
D.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
E.
withdrewInFavorOf
Indicates that one party retracted or gave up its position, claim, or candidacy in support of another party.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.