Triple
T23372353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fellow of the Royal Academy of Sciences |
E593507
|
entity |
| Predicate | isTypicallyFor |
P18991
|
FINISHED |
| Object | senior researchers |
—
|
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: senior researchers | Statement: [Fellow of the Royal Academy of Sciences, isTypicallyFor, senior researchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyFor Context triple: [Fellow of the Royal Academy of Sciences, isTypicallyFor, senior researchers]
-
A.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
B.
isSuitableFor
chosen
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
C.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
D.
hasTypicalUsageRegion
Indicates that something is most commonly or characteristically used within a particular geographic region.
-
E.
isTypicallyPlayed
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.