Triple
T14114866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miaoux Miaoux |
E339741
|
entity |
| Predicate | activeAs |
P112874
|
FINISHED |
| Object | solo project |
—
|
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: solo project | Statement: [Miaoux Miaoux, activeAs, solo project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAs Context triple: [Miaoux Miaoux, activeAs, solo project]
-
A.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
B.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
C.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
D.
isActive
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
E.
activeAround
Indicates that an entity is performing actions or exhibiting activity in the vicinity of another entity or location.
- F. None of above. chosen
Provenance (4 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600f992c81908133813f2894dcca |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.